Portable computing device and method for transmitting instructor operating station (IOS) filtered information

ABSTRACT

A portable computing device and method for transmitting Instructor Operating Station (IOS) filtered information. A portable computing device receives IOS control and monitoring data from a simulation server, displays the IOS control and monitoring data on the portable computing device, and receives a selection by a user of at least one component of the displayed IOS control and monitoring data. The selection is performed by an interaction of the user with the displayed IOS control and monitoring data. The portable computing device determines IOS filtered information related to the selected at least one component, and transmits the IOS filtered information to a destination computing device. The determination of the IOS filtered information takes into consideration destination user access rights of a destination user. The destination device may be a simulator or a portable computing device, where the destination user performs a simulation session by interacting with the simulation server.

TECHNICAL FIELD

The present disclosure relates to the field of simulators. Morespecifically, the present disclosure relates to a portable computingdevice and method for transmitting Instructor Operating Station (IOS)filtered information.

BACKGROUND

Flight simulators are used by commercial airlines and air forces totrain their pilots to face various types of situations. A simulator iscapable of simulating various functionalities of an aircraft, and ofreproducing various operational conditions of a flight (e.g. takeoff,landing, hovering, etc.). A trainee (e.g. a pilot performing a trainingsession) interacts with the simulator to control various functionalitiesof the simulated aircraft during a simulation executed by the simulator.Similarly, an instructor (e.g. an experienced pilot) may interact withthe simulator for various purposes, including controlling a simulationcurrently executed by the simulator, creating or updating simulationscenarios, controlling the simulation environment of a trainee, etc.

The instructor may control the simulation currently executed by thesimulator, and performed by the trainee(s), via a portable computingdevice displaying a dedicated Graphical User Interface (GUI) on adisplay of the portable computing device. The dedicated GUI displaysspecific information accessible to the instructor, but not to thetrainee. However, in some particular circumstances, the instructor maywant to share some of the information displayed in the dedicated GUIwith the trainee.

Therefore, there is a need for a portable computing device and methodfor transmitting Instructor Operating Station (IOS) filteredinformation.

SUMMARY

According to a first aspect, the present disclosure provides a portablecomputing device capable of transmitting Instructor Operating Station(IOS) filtered information. The portable computing device comprising adisplay, a user interface for allowing interactions of a user with theportable computing device, and a communication interface for exchangingdata with other entities. The portable computing device also comprises aprocessing unit for receiving IOS control and monitoring data from asimulation server via the communication interface. The processing unitfurther displays the IOS control and monitoring data on the display. Theprocessing unit further receives a selection by the user of at least onecomponent of the IOS control and monitoring data displayed on thedisplay via the user interface. The processing unit further determinesIOS filtered information related to the selected at least one component.The determination of the IOS filtered information takes intoconsideration destination user access rights of a destination user. Theprocessing unit further transmits the IOS filtered information to adestination computing device via the communication interface.

According to a second aspect, the present disclosure provides a methodfor transmitting Instructor Operating Station (IOS) filteredinformation. The method comprises receiving by a processing unit of aportable computing device IOS control and monitoring data from asimulation server via a communication interface of the portablecomputing device. The method comprises displaying by the processing unitthe IOS control and monitoring data on a display of the portablecomputing device. The method comprises receiving by the processing unita selection by a user of at least one component of the IOS control andmonitoring data displayed on the display. The selection is performed byan interaction of the user with the displayed IOS control and monitoringdata via a user interface of the portable computing device. The methodcomprises determining by the processing unit IOS filtered informationrelated to the selected at least one component. The determination of theIOS filtered information takes into consideration destination useraccess rights of a destination user. The method comprises transmittingby the processing unit the IOS filtered information to a destinationcomputing device via the communication interface.

According to a third aspect, the present disclosure provides anon-transitory computer program product comprising instructionsdeliverable via an electronically-readable media, such as storage mediaand communication links. The instructions when executed by a processingunit of a portable computing device providing for transmittingInstructor Operating Station (IOS) filtered information by implementingthe aforementioned method.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the disclosure will be described by way of example onlywith reference to the accompanying drawings, in which:

FIG. 1 illustrates a legacy simulator configuration;

FIGS. 2A, 2B and 2C illustrate a simulation server interacting with asimulator and portable computing devices for executing a simulation;

FIGS. 3A, 3B and 3C respectively illustrate exemplary embodiments ofcomponents and functionalities of the simulation server, simulator andportable computing devices of FIGS. 2A, 2B and 2C;

FIG. 4 illustrates a simulation server concurrently interacting with aplurality of simulators and portable computing devices;

FIG. 5 illustrates respective displays of the simulator and portablecomputing device of FIGS. 3B and 3C;

FIGS. 6A, 6B and 6C represent an exemplary flow diagram illustratinginteractions between components of the simulation server of FIG. 3A andthe portable computing device of FIG. 3C;

FIGS. 7A, 7B, 7C and 7D illustrate the transmission of InstructorOperating Station (IOS) filtered information by the portable computingdevice of FIG. 3C;

FIG. 8 represents the portable computing device of FIG. 3C adapted forthe transmission of IOS filtered information;

FIG. 9 represents a method for transmitting IOS filtered information;and

FIGS. 10A and 10B illustrate the transfer of IOS filtered informationconsisting of filtered IOS User Interface (UI) pages.

DETAILED DESCRIPTION

The foregoing and other features will become more apparent upon readingof the following non-restrictive description of illustrative embodimentsthereof, given by way of example only with reference to the accompanyingdrawings. Like numerals represent like features on the various drawings.

Various aspects of the present disclosure generally address one or moreof the problems related to the transmission of a subset of datacurrently displayed on a display of a portable computing device, thedisplayed data allowing a user of the portable computing device tocontrol the execution of a simulation executed on a simulation server.The subset of data is transmitted to a destination computing devicewhere a destination user is performing a simulation session related tothe simulation executed on the simulation server. The subset of data tobe transmitted is determined based on particular user access rights ofthe destination user. Although the examples provided in the rest of thedisclosure are in the field of aircraft simulators, the teachings of thepresent disclosure can also be applied to simulators of terrestrialvehicles such as tanks, maritime vehicles such as boats, etc. Thesimulators may also perform a real time simulation of an undergroundsystem, a mining facility, a nuclear plant, a human body, etc.

Simulation Server

Referring now to FIG. 1, a legacy simulator 100 is represented. Thesimulator 100 executes a simulation. The execution of the simulation isgenerally performed in real time and encompasses a plurality offunctions, which are performed sequentially or concurrently.

The execution of the simulation comprises executing one or moresimulation functionalities 110. In the case of an aircraft simulator,examples of simulation functionalities 110 include simulations of thefollowing components of the aircraft: simulation of the engines,simulation of the landing gear, simulation of the electrical circuits,simulation of the hydraulic circuits, simulation of the cockpit, etc.Furthermore, the execution of particular simulation functionality 110may trigger the display of generated simulation data (e.g. in the formof a navigation map, a radar map, a weather map, a flight map, aircraftdata, etc.) on a display of the simulator 100. Simulationfunctionalities 110 can be implemented separately in software modulesexecuted by the simulator 100, or grouped per category of equipment,type of simulation, etc. into larger software modules. The simulator 100is capable of executing several simulation functionalities 110 inparallel, to perform an exhaustive simulation of the aircraft.Alternatively, the simulator 100 executes a single simulationfunctionality 110 (or a limited number of simulation functionalities110) to perform a restricted simulation of the aircraft, focusing onspecific systems and sub-systems of the aircraft (e.g. only the engines,only the engines and landing gear in combination, etc.).

The execution of the simulation also comprises executing a simulatorGraphical User Interface (GUI) functionality 130. The simulator GUIfunctionality 130 allows a user 20 (for example a trainee) to interactwith the simulator 100, and more specifically with the simulationfunctionalities 110 currently executed by the simulator 100. In the caseof an aircraft simulator, the simulator GUI functionality 130 comprisesdisplaying simulation data generated by the simulation functionalities110 on one or more displays of the simulator 100. The displayedsimulation data may include flight parameters (e.g. altitude, speed,etc.), aircraft parameters (e.g. remaining fuel, alarms, etc.), maps(e.g. navigation map, weather map, radar map, etc.), virtual controls,out-of window information, etc. The simulator GUI functionality 130 alsocomprises receiving interactions from the user 20 via one or more userinterfaces of the simulator 100. The user interface(s) may includetraditional computer user interfaces (e.g. a keyboard, a mouse, atrackpad, a touch screen, etc.), as well as dedicated simulation userinterfaces (e.g. switches, simulation command controls, joysticks,etc.). The interactions received from the user 20 are processed by thesimulation functionalities 110, and affect the simulation of one or moresystems of the aircraft.

The execution of the simulation also comprises executing an InstructorOperating Station (IOS) functionality 120. The IOS functionality 120allows a user 10 (for example an instructor) to interact with thesimulator 100, and more specifically with the simulation functionalities110 currently executed by the simulator 100. For instance, IOS UserInterface (UI) pages are displayed on a display of the simulator 100,allowing the user 10 to control in real time the execution of aparticular simulation scenario executed by the simulationfunctionalities 110. The IOS 120 comprises graphical control elements(e.g. menus and sub-menus, list boxes, etc.) for controlling theexecution of the simulation (e.g. modifying simulation parameters) andgraphical display elements (e.g. images, text fields, icons, embeddedvideos, etc.) for displaying simulation data generated by the simulationfunctionalities 110. In the case of an aircraft simulator, the user 10interacts with the IOS 120 via one or more user interfaces (e.g. akeyboard, a mouse, a trackpad, a touch screen, etc.) to configure and/orupdate simulation parameters (e.g. weather conditions, flight plan,etc.). The configured/updated simulation parameters are processed by thesimulation functionalities 110, and affect the simulation of one or moresystems of the aircraft.

In a particular embodiment, the execution of the simulation alsocomprises executing at least one proxy function (not represented in FIG.1). The proxy function allows other functionalities of the simulator 100(e.g. IOS functionality 120 and simulator GUI functionality 130) tointeract with the simulation functionalities 110. A plurality of proxyfunctions may be executed concurrently, each proxy function providing aninterface to a specific functionality among the simulationfunctionalities 110.

Referring now concurrently to FIGS. 2A, 2B and 2C, embodiments of asimulation server 200 and a simulator 300 in accordance with the presentinvention are represented. The present simulation server 200 andsimulator 300 rely on sharing processing performed when executing asimulation between themselves.

The simulation server 200 executes a simulation, which comprisesexecuting one or more server simulation functionalities 210, executing aserver IOS functionality 220, and executing a server graphical userinterface (GUI) functionality 230. The simulator 300 also executes thesimulation, which comprises executing one or more simulator simulationfunctionalities 310, executing a simulator IOS User Interface (UI) 320,and executing a simulator graphical user interface (GUI) 330.

The simulation functionalities 110 of the legacy simulator 100 have beensplit between the server simulation functionalities 210 and thesimulator simulation functionalities 310. The server simulationfunctionalities 210 perform the computations for simulating theoperations of the simulated entity. The present simulation server 200and simulator 300 may be used to simulate any type of entity, such asfor example aircrafts, spatial shuttles, vessels, vehicles, etc. Forsimplicity purposes, the following description will provide examplesrelated to aircrafts. Such examples are provided for example purposesonly, and should not be construed to limit the scope of protectionsought for the present simulation server 200 and simulator 300.

The server simulation functionalities 210 may perform computations forsimulating components of the vehicle being simulated, for exampleengines, electrical circuits, hydraulic circuits, information shown anddisplayed to a user of the simulator, etc. The server simulationfunctionalities 210 generate simulation data 211, which are used locallyby other functionalities implemented by the simulation server 200 (e.g.the server IOS functionality 220 and the server GUI functionality 230).The server simulation functionalities 210 also generate simulation data212, which are transmitted to the simulator 300 through a communicationnetwork 30. The transmitted simulation data 212 can be used by thesimulator GUI 330, the simulator IOS UI 320 and the simulator simulationfunctionalities 310, but may also be used by other functionalitiesimplemented by the simulator 300 (this use case is not represented inFIG. 2A). The simulation data 212 include visual data in the form ofstatic 2D or 3D simulation images, or a flow of 2D or 3D simulationimages. Examples of visual data include a navigation map, a radar map, aweather map, a flight map, aircraft data, etc. For instance, a map mayconsist in a static 2D or 3D image, or a flow of 2D or 3D imagescorresponding to a real time streaming of the map. The visual data aredisplayed by at least one simulator GUI 330 and simulator IOS UI 320 ondisplay(s) of the simulator 300. The simulation data 212 may alsoinclude actuation data, which are processed by the simulator simulationfunctionalities 310 for actuating physical component(s) of the simulator300 (e.g. actuating hydraulic cylinders for moving a simulated controlcabin representative of the entity). The simulator simulationfunctionalities 310 may also perform local computations for simulatingsome of the operations of the simulated entity, which are not performedby the server simulation functionalities 210. The simulator simulationfunctionalities 310 also generate feedback simulation data 212, whichare transmitted to the simulation server 200 through the communicationnetwork 30. These feedback simulation data 212 are representative of anoperational status of the simulator 300, and are used by the serversimulation functionalities 210 as a feedback for taking intoconsideration the operational status of the simulator 300 when executingthe simulation. For example, the server simulation functionalities 210transmit simulation data 212 for actuating (by the simulator simulationfunctionalities 310) a physical component of the simulator 300, and thesimulator simulation functionalities 310 transmit feedback simulationdata 212 indicating that the activation of the physical component of thesimulator 300 has been completed. Upon reception of the feedbacksimulation data 212, the server simulation functionalities 210 proceedwith the next step in the execution of the simulation, taking intoconsideration the new operational status of the simulator 300.

The IOS functionality 120 of the legacy simulator 100 has also beensplit between the server IOS functionality 220 and the simulator IOS UI320. The server IOS functionality 220 performs the computations relatedto the IOS functionality, while the simulator IOS UI 320 performs theinteractions with a user 10. The server IOS functionality 220 generatesIOS control and monitoring data 222, which are transmitted to thesimulator 300 through the communication network 30. The IOS control andmonitoring data 222 are used by the simulator IOS UI 320 for interactingwith the user 10. The IOS control and monitoring data 222 includes IOSUI page(s), e.g. each IOS UI page corresponding to a user interface withsub-groups of instances, which are displayed on a display of thesimulator 300 by the simulator IOS UI 320. The displayed IOS UI page(s)allow the user 10 to control in real time (at the simulator 300) theexecution of a particular simulation scenario executed by the serversimulation functionalities 210. More specifically, by interacting withthe IOS UI 320, the user 10 generates IOS interaction data 222 (e.g.configuration, monitoring and/or update of simulation parameters), whichare transmitted via the network 30 to the server IOS functionality 220.The server IOS functionality 220 interacts with the server simulationfunctionalities 210 by exchanging data 211. As mentioned previously, thedata 211 include simulation data generated by the server simulationfunctionalities 210, and used by the server IOS functionality 220 forgenerating IOS UI pages(s), which are transmitted to the simulator IOSUI 320. The data 211 also include the configuration/update of simulationparameters received from the simulator IOS UI 320, which may bepre-processed by the server IOS functionality 220 before transmission tothe server simulation functionalities 210. The server simulationfunctionalities 210 use the configuration/update of simulationparameters to control the execution of the simulation. As mentionedpreviously, the simulator IOS UI 320 also receives simulation data 212(e.g. 2D or 3D maps) from the server simulation functionalities 210,displayed on display(s) of the simulator 300.

The simulator GUI functionality 130 of the legacy simulator 100 has alsobeen split between the server GUI functionality 230 and the simulatorGUI 330. The server GUI functionality 230 performs the computationsrelated to the graphical representations to be displayed to the user 20,while the simulator GUI 330 performs the interactions with the user 20.The server GUI functionality 230 generates graphical user interface(GUI) graphical data 232, which are transmitted to the simulator 300through the communication network 30. The GUI graphical data 232 areused by the simulator GUI 330 for interacting with the user 20. The GUIgraphical data 232 include simulation parameters, events and information(e.g. entity parameters, events, maps, etc.), which are displayed ondisplay(s) of the simulator 300 by the simulator GUI 330. The displayedGUI graphical data 232 allow the user 20 to interact in real time (atthe simulator 300) with the execution of a particular simulationscenario executed by the server simulation functionalities 210. Morespecifically, based on the displayed GUI graphical data 232, the user 20interacts with one or more user interfaces of the simulator 300. Thesimulator GUI 330 generates GUI interaction data 232 corresponding tothe user 20 interactions, which are transmitted via the network 30 tothe server GUI functionality 230. The server GUI functionality 230interacts with the server simulation functionalities 210 by exchangingdata 211. As mentioned previously, the data 211 include simulation datagenerated by the server simulation functionalities 210, and used by theserver GUI functionality 230 for generating the simulation parameters,events and information transmitted to the simulator GUI 330. The data211 also include the user 20 interactions received from the simulatorGUI 330, which may be pre-processed by the server GUI functionality 230before transmission to the server simulation functionalities 210. Theserver simulation functionalities 210 use the user 20 interactions tocontrol the execution of the simulation. As mentioned previously, thesimulator GUI 330 also receives simulation data 212 (e.g. 2D or 3D maps)from the server simulation functionalities 210, which are furtherdisplayed on the simulator 300 through the simulator GUI 330.

In a particular embodiment, at least one of the functionalitiesimplemented by the legacy simulator 100 of FIG. 1 may not be deported onthe simulation server 200, but fully implemented on the simulator 300.For example, the simulation server 200 does not include the server GUIfunctionality 230 and the simulator 300 includes the simulator GUIfunctionality 130 of the legacy simulator 100 in place of the simulatorGUI 330. In this particular embodiment, the simulator GUI 130 isimplemented on the simulator 300 and interacts directly with the serversimulation functionalities 210 via the network 30. This embodiment isnot represented in the Figures.

The network 30 may consist of a mobile network (e.g. a Wi-Fi network orcellular network), a fixed network (e.g. an Ethernet network), acombination thereof, etc. The network 30 may allow communicationsbetween devices over an Intranet, an Extranet, the global Internet, etc.The simulation server 200 and the simulator 300 both include acommunication interface compatible with the network 30, for exchangingdata over the network 30. For example, the simulation server 200 and thesimulator 300 comprise a communication interface supporting both Wi-Fiand Ethernet, to easily adapt to a particular network 30 deployed at thepremises where they are respectively operating.

Although not represented in FIG. 2A for simplification purposes, theserver simulation functionalities 210 generally comprise a plurality offunctions, for example a Weather function and a Navigation function(represented and described later with respect to FIG. 3A). TheNavigation function of the server simulation functionalities 210interfaces with other functionalities of the simulation server 200 (e.g.with the server GUI functionality 230 and with a dedicated IOS functionIOS_1 (represented in FIG. 3A) of the server IOS functionality 220).Similarly, the Weather function of the server simulation functionalities210 interfaces with other functionalities of the simulation server 200(e.g. with the server GUI functionality 230 and with a dedicated IOSfunction IOS_2 (represented in FIG. 3A) of the server IOS functionality220). As mentioned previously with respect to the legacy simulatorrepresented in FIG. 1, a plurality of proxy functions may be used tointerface the functions (e.g. Navigation and Weather respectively) ofthe server simulation functionalities 210 with other functionalities ofthe simulation server 200 (e.g. the server IOS functionality 220 and theserver GUI functionality 230).

In the rest of the description, the simulation data 212 generated andtransmitted by the server simulation functionalities 210 to thesimulator 300 may be referred to as simulator simulation data. The IOScontrol and monitoring data 222 generated and transmitted by the serverIOS functionality 220 to the simulator 300 may be referred to assimulator IOS control and monitoring data. The GUI graphical data 232generated and transmitted by the server GUI functionality 230 to thesimulator 300 may be referred to as simulator graphical data.

The IOS interaction data 222 generated and transmitted by the simulatorIOS UI 320 to the simulation server 200 and the GUI interaction data 232generated and transmitted by the simulator GUI 330 to the simulationserver 200 may be referred to as simulator interaction data.

Referring now concurrently to FIGS. 2A and 2B, portable computingdevices 400 and 400′ are represented in FIG. 2B. The portable computingdevices 400 and 400′ implement some of the functionalities implementedon the simulator 300 represented in FIG. 2A.

The portable computing device 400 and 400′ may consist in various typesof computing devices having a form factor allowing easy carrying.Examples of such portable computing devices 400 and 400′ includelaptops, tablets, etc. The portable computing devices 400 and 400′ bothinclude a communication interface compatible with the network 30, forexchanging data with the simulation server 200 over the network 30.

The portable computing device 400 implements a portable computing deviceIOS UI 420 similar to the simulator IOS UI 320. The portable computingdevice IOS UI 420 exchanges IOS data 222 (10S control and monitoringdata, and IOS interaction data) with the server IOS functionality 220over the network 30, in a similar manner as the simulator IOS UI 320.The portable computing device IOS UI 420 allows the user 10 to controlin real time, via the portable computing device 400, the execution of aparticular simulation scenario executed by the server simulationfunctionalities 210. The portable computing device IOS UI 420 alsoreceives simulation data 212 (e.g. 2D or 3D maps) from the serversimulation functionalities 210, which are further displayed on theportable computing device 400 through the portable computing device IOSUI 420.

In this configuration, the IOS functionality 120 of the legacy simulator100 represented in FIG. 1 has been split between the server IOSfunctionality 220 and the portable computer device IOS UI 420. Theserver IOS functionality 220 performs the computations related to theIOS functionality, while the portable computing device IOS UI 420performs the interactions with the user 10.

The server IOS functionality 220 is adapted for simultaneously oralternatively supporting interactions with the simulator IOS UI 320 andthe portable computing device IOS UI 420. For example, the same user 10can use the simulator IOS UI 320 during a first simulation session, andthe portable computing device IOS UI 420 during a second simulationsession, both sessions being performed by executing server simulationfunctionalities 210. In another example, a first user 10 uses thesimulator IOS UI 320 during a simulation session (for controlling afirst simulation functionality), and a second user 10 simultaneouslyuses the portable computing device IOS UI 420 during the same simulationsession (for controlling a second simulation functionality), thesimulation session being performed by executing the server simulationfunctionalities 210.

The portable computing device 400′ implements a portable computingdevice graphical user interface (GUI) 430 similar to the simulator GUI330. The portable computing device GUI 430 exchanges GUI graphical dataand GUI interaction data 232 with the server GUI functionality 230 overthe network 30, in a similar manner as the simulator GUI 330. Theportable computing device GUI 430 allows the user 20 to interact in realtime, via the portable computing device 400′, with the execution of aparticular simulation scenario executed by the server simulationfunctionalities 210. As mentioned previously, the portable computingdevice GUI 430 also receives and displays simulation data 212 (e.g. 2Dor 3D maps) from the server simulation functionalities 210.

In this configuration, the simulator GUI functionality 130 of the legacysimulator 100 represented in FIG. 1 has been split between the serverGUI functionality 230 and the portable computing device GUI 430. Theserver GUI functionality 230 performs the computations related to thegraphical representations to be displayed to the user 10, while theportable computing device GUI 430 performs the interactions with theuser 20.

The server GUI functionality 230 is adapted for simultaneously oralternatively supporting interactions with the simulator GUI 330 and theportable computing device GUI 430. For example, user 20 can use thesimulator GUI 330 during a first training session, and the portablecomputing device GUI 430 during a second training session, bothsimulation sessions being performed by executing server simulationfunctionalities 210. In another example, a first user 20 uses thesimulator GUI 330 during a simulation session (for interacting with afirst simulation functionality 210), and a second user 20 simultaneouslyuses the portable computing device GUI 430 during the same simulationsession (for interacting with a second simulation functionality 210),the simulation sessions being performed by executing the first andsecond server simulation functionalities 210.

In the rest of the description, the simulation data 212 generated andtransmitted by the server simulation functionalities 210 to a portablecomputing device 400 or 400′ may be referred to as portable computingdevice simulation data.

The IOS control and monitoring data 222 generated and transmitted by theserver IOS functionality 220 to a portable computing device 400 may bereferred to as portable computing device IOS control and monitoringdata. The GUI graphical data 232 generated and transmitted by the serverGUI functionality 230 to a portable computing device 400′ may bereferred to as portable computing device graphical data. The IOSinteraction data 222 generated and transmitted by the portable computingdevice IOS UI 420 to the simulation server 200 and the GUI interactiondata 232 generated and transmitted by the portable computing device GUI430 to the simulation server 200 may be referred to as portablecomputing device interaction data.

FIG. 2C illustrates another operational configuration of the simulationserver 200 and simulator 300. In this particular configuration, the user10 uses the portable computing device IOS UI 420 for controlling in realtime (through the server IOS functionality 220) the execution of aparticular simulation scenario executed by the server simulationfunctionalities 210. The user 20 uses the simulator GUI 330 forinteracting in real time (through the server GUI functionality 230) withthe execution of the same particular simulation scenario executed by theserver simulation functionalities 210.

A person skilled in the art will readily understand that the usage ofthe simulation server 200 provides the required flexibility forimplementing a plurality of other operational configurations involvingthe simulation server 200, the simulator 300 and portable computingdevice(s) (e.g. 400 and 400′), which have not been represented in theFigures for simplification purposes.

Referring now to FIGS. 3A, 3B and 3C, exemplary embodiments ofcomponents and functionalities of the simulation server 200, thesimulator 300 and the portable computing device 400 are represented.

Referring more specifically to FIG. 3A, the simulation server 200comprises a processing unit 201, having one or more processors (notrepresented in FIG. 3A for simplification purposes) capable of executinginstructions of computer program(s). Each processor may further have oneor several cores. The processing unit 201 implements functionalities ofthe simulation server 200 by executing computer program(s) instructions.The functionalities implemented by the processing unit 201 include theserver simulation functionalities 210, the server IOS functionality 220and the server GUI functionality 230.

The simulation server 200 comprises memory 202 for storing instructionsof the computer program(s) executed by the processing unit 201, datagenerated by the execution of the computer program(s), data received viaa communication interface 203, etc. The simulation server 200 maycomprise several types of memories, including volatile memory,non-volatile memory, etc.

The simulation server 200 comprises the communication interface 203, forexchanging data with other devices, including one or more simulators 300and/or one or more portable computing devices 400 via the network 30.The exchanged data comprise the IOS data 222, the GUI data 232 and thesimulation data 212 represented in FIGS. 2A and 2B. The communicationinterface 203 supports one of more communication protocols, such asWi-Fi, Ethernet, etc.

The simulation server 200 may comprise a display 204 (e.g. a regularscreen or a tactile screen) for displaying data processed and/orgenerated by the processing unit 201. The simulation server 200 may alsocomprise one or more user interface 205 (e.g. a mouse, a keyboard, atrackpad, a touchscreen, etc.) for allowing a user to interact directlywith the simulation server 200.

The server IOS functionality 220, the server simulation functionalities210, and the server GUI functionality 230 are implemented by one or morecomputer programs. Each computer program comprises instructions forimplementing the corresponding function when executed by the processingunit 201. The instructions are comprised in a non-transitory computerprogram product (e.g. memory 202). The instructions are deliverable viaan electronically-readable media, such as a storage media (e.g. a USBkey or a CD-ROM) or the network 30 (through the communication interface203).

Referring more specifically to FIG. 3B, the simulator 300 comprises aprocessing unit 301, having one or more processors (not represented inFIG. 3B for simplification purposes) capable of executing instructionsof computer program(s). Each processor may further have one or severalcores. The processing unit 301 implements functionalities of thesimulator 300 by executing instructions of the computer program(s). Thefunctionalities implemented by the processing unit 301 include thesimulator simulation functionalities 310, the simulator IOS UI 320 andthe simulator GUI 330.

The simulator 300 comprises memory 302 for storing instructions of thecomputer program(s) executed by the processing unit 301, data generatedby the execution of the computer program(s), data received via acommunication interface 303, etc. The simulator 300 may comprise severaltypes of memories, including volatile memory, non-volatile memory, etc.

The simulator 300 comprises the communication interface 303, forexchanging data with other devices, including the simulation server 200via the network 30. The exchanged data comprise the IOS data 222, theGUI data 232 and the simulation data 212 represented in FIG. 2A. Thecommunication interface 303 supports one of more communicationprotocols, such as Wi-Fi, Ethernet, etc.

The simulator comprises one or more actuators 306 for actuating physicalcomponent(s) of the simulator 300 (for example. actuating hydrauliccylinders for moving a simulated control cabin of an aircraft) under thecontrol of the simulator simulation functionalities 310 executed by theprocessing unit 301.

The simulator 300 comprises one or more displays 304 (e.g. a regularscreen or a tactile screen) for displaying data processed and/orgenerated by the processing unit 301. The simulator 300 also comprisesone or more user interface 305 (e.g. traditional computer userinterfaces as well as dedicated simulation user interfaces) for allowingusers to interact with the simulator 300.

In a particular embodiment, the simulator IOS UI 320 includes a displayfunction 321 and an interaction function 322. The display function 321processes the IOS control and monitoring data 222 and the simulationdata 212 of FIG. 2A, received from the simulation server 200 via thecommunication interface 303, and displays the processed IOS control andmonitoring data 222 and simulation data 212 on the display 304.

The simulator IOS UI interaction function 322 generates the IOSinteraction data 222 of FIG. 2A based on the interactions of the user 10(via the user interface(s) 305) with the processed IOS control andmonitoring data 222 displayed on the display 304. The IOS interactiondata 222 are transmitted to the server IOS functionality 220 of thesimulation server 200 through the communication interface 303.

The simulator GUI 330 may also include a display function and aninteraction function, not represented in FIG. 3B for simplificationpurposes. The display function processes the GUI graphical data 232 andthe server simulation data 212 of FIG. 2A, received from the simulationserver 200 via the communication interface 303, and displays theprocessed GUI graphical data 232 and server simulation data 212 on thedisplay 304.

The interaction function of the simulator GUI 330 generates the GUIinteraction data 232 of FIG. 2A based on the interactions of the user 20(via the user interface(s) 305) with the processed GUI graphical data232 displayed on the display 304. The GUI interaction data 232 aretransmitted to the server GUI functionality 230 of the simulation server200 through the communication interface 303.

In another particular embodiment, the simulator simulationfunctionalities 310 include a display function 311 and an actuationfunction 312. The display function 311 processes simulation data 212 ofFIG. 2A received from the simulation server 200 via the communicationinterface 303, and displays the processed simulation data on the display304. The display function 311 can be used for displaying the simulationdata 212 of FIG. 2A which cannot be displayed via the simulator IOS UI320 or the simulator GUI 330.

The actuation function 312 processes other simulation data 212 of FIG.2A which include actuation data, received from the simulation server 200via the communication interface 303. The actuation function 312processes the received actuation data and actuates a correspondingactuator 306. The actuation function 312 also generates feedbackactuation data representative of a state of the actuated correspondingactuator 306. The feedback actuation data are transmitted to thesimulation server 200 through the communication interface 303. Morespecifically, simulation data 212 of FIG. 2A comprising the feedbackactuation data are transmitted to the server simulation functionalities210 represented in FIG. 3A.

The simulator simulation functionalities 310, the simulator IOS UI 320,and the simulator GUI 320 are implemented by one or more computerprograms. Each computer program comprises instruction for implementingthe corresponding function when executed by the processing unit 301. Theinstructions are comprised in a non-transitory computer program product(e.g. memory 302). The instructions are deliverable via anelectronically-readable media, such as a storage media (e.g. a USB keyor a CD-ROM) or the network 30 (through the communication interface303).

Referring more specifically to FIG. 3C, the portable computing device400 comprises a processing unit 401, having one or more processors (notrepresented in FIG. 3C for simplification purposes) capable of executinginstructions of computer program(s). Each processor may further have oneor several cores. The processing unit 401 implements functionalities ofthe portable computing device 400 by executing instructions of thecomputer program(s). The functionalities implemented by the processingunit 401 include the portable computing device IOS UI 420.

The portable computing device 400 comprises memory 402 for storinginstructions of the computer program(s) executed by the processing unit401, data generated by the execution of the computer program(s), datareceived via a communication interface 403, etc. The portable computingdevice 400 may comprise several types of memories, including volatilememory, non-volatile memory, etc.

The portable computing device 400 comprises the communication interface403, for exchanging data with other devices, including the simulationserver 200 via the network 30. The exchanged data comprise the IOS data222 and the simulation data 212 represented in FIG. 2B. Thecommunication interface 403 supports one of more communicationprotocols, such as Wi-Fi, Ethernet, etc.

The portable computing device 400 comprises a display 404 (e.g. aregular screen or a tactile screen) for displaying data processed and/orgenerated by the processing unit 401. The portable computing device 400also comprises at least one user interface 405 (e.g. a mouse, akeyboard, a trackpad, a touchscreen, etc.) for allowing a user (notrepresented in FIG. 3C) to interact with the portable computing device400.

In a particular embodiment, the portable computing device IOS UI 420includes a display function 421 and an interaction function 422. Thedisplay function 421 and interaction function 422 operate in a similarmanner as the display function 321 and interaction function 322represented in FIG. 3B.

The portable computing device IOS UI 420 is implemented by one or morecomputer programs. Each computer program comprises instruction forimplementing the corresponding function when executed by the processingunit 401. The instructions are comprised in a non-transitory computerprogram product (e.g. memory 402). The instructions are deliverable viaan electronically-readable media, such as a storage media (e.g. a USBkey or a CD-ROM) or the network 30 (through the communication interface403).

In an alternative embodiment not represented in the Figures forsimplification purposes, the portable computing device 400 of FIG. 3Cmay correspond to the portable computing device 400′ represented in FIG.2B. The functionalities implemented by the processing unit 401 includethe portable computing device GUI 430 of FIG. 2B in place of theportable computing device IOS UI 420. The data exchanged with thesimulation server 200 comprise the GUI data 232 and the simulation data212 of FIG. 2B.

In still another alternative embodiment not represented in the Figuresfor simplification purposes, the portable computing device 400 of FIG.3C may be adapted for implementing both the portable computing deviceIOS UI 420 and the portable computing device GUI 430 illustrated in FIG.2B. If user 10 is using the portable computing device 400, the portablecomputing device IOS UI 420 is executed by the processing unit 401. Ifuser 20 is using the portable computing device 400, the portablecomputing device GUI 430 illustrated in FIG. 2B is executed by theprocessing unit 401.

In a particular aspect, the processing unit 201 of the simulation server200 further executes a web server function 250, for implementing theexchange of data between the simulation server 200 and the simulator 300or the portable computing devices 400. One of the users 10 or 20 (forexample an instructor or a trainee) initiates a simulation web sessionbetween the web server function 250 and a web client implemented by thesimulator 300 or portable computing devices 400, as will be detailedlater in the description. Once the simulation web session is set up,data can be exchanged between the simulation server 200 and thesimulator 300 or portable computing devices 400 via the web serverfunction 250. The simulation data 212, the IOS data 222, and the GUIdata 232 represented in FIGS. 2A and 2B are exchanged via the web serverfunction 250.

In another particular aspect, the processing unit 201 of the simulationserver 200 further executes at least one rendering function 240. Eachinstance of rendering function 240 is launched by the web serverfunction 250, after the aforementioned simulation web session has beeninitiated, as will be detailed later in the description. Each instanceof rendering function 240 generates data adapted for rendering on aspecific destination device. For example, if the specific destinationdevice is the portable computing device 400, data such as 2D or 3Dsimulation images may need to be adapted to the particular processingand display capabilities of the portable computing device 400. If thespecific destination device is the simulator 300, these data may notneed a specific adaptation for rendering on the simulator 300. Thus,data which do not need to be adapted are transmitted directly by the webserver function 250, while data which need to be adapted (e.g. 2D or 3Dsimulation images) are processed by an instance of rendering function240 for adaptation purposes. The adapted data may be transmitted by therendering function 240 to a destination device. Alternatively, theadapted data are also transmitted via the web server function 250 to adestination device. For illustration purposes, in the rest of thedescription, the adapted data will be transmitted by the renderingfunction 240 to a destination device (e.g. portable computing device400). Usually, some of the simulation data 212 represented in FIGS. 2Aand 2B contain 2D or 3D simulation images such as maps, which need to beadapted by an instance of rendering function 240, in particular fortransmission to a portable computing device 400 with limited processingcapabilities, display capabilities, etc. However, some of the IOS data222 and GUI data 232 represented in FIGS. 2A and 2B may also be adaptedby an instance of rendering function 240 when needed.

The adaptation of a static 2D or 3D simulation image (or a flow of 2D or3D simulation images) by an instance of rendering function 240 mayconsist in one of the following: encoding the simulation image(s) in aparticular format (e.g. JPEG, GIF, TIFF, PNG, etc.), applying aparticular compression algorithm to the simulation image(s), applying aparticular image sampling algorithm to the simulation image(s), andapplying a particular algorithm for lowering an image resolution of thesimulation image(s).

Since at least some of the communications with the simulation server 200are performed through the web server function 250, the processing unit301 of the simulator 300 and the processing unit 401 of the portablecomputing device 400 respectively execute a web client function 350 and450. The web client functions 350 and 450 are used for establishing thepreviously described simulation web session with the web server function250 of the simulation server 200. The web client functions 350 and 450are further used for exchanging data (e.g. simulation data 212, IOS data222 and GUI data 232 represented in FIGS. 2A and 2B) with the web serverfunction 250 of the simulation server 200. For instance, datatransmitted by the web server function 250 to the simulator IOS UI 320are received by the web client function 350, and forwarded to thesimulator IOS UI 320. Data to be transmitted by the simulator IOS UI 320to the simulation server 200 are transmitted to the web client function350, which forwards them to the web server function 250. The use of aweb client for exchanging data is well known in the art, and will not befurther detailed in the rest of the description.

With respect to the adapted data transmitted by an instance of renderingfunction 240 of the simulation server 200, they are not received by aweb client (e.g. 450 on the portable computing device 400), but receiveddirectly by the destination functionality (e.g. portable computingdevice IOS UI 420). A proprietary communication protocol usingpre-defined or dynamically allocated communication sockets can be usedfor transmitting the adapted data, as is well known in the art.

For illustration purposes, the operations of the web server function 250and the rendering functions 240 will now be detailed in the context ofan exchange of data between the simulation server 200 and the portablecomputing device 400. In this context, some of the data transmitted bythe simulation server 200 need to be adapted to the capabilities of theportable computing device 400 by one or more instances of renderingfunction 240, while other data can be transmitted directly via the webserver function 250.

The data adapted for rendering on a particular destination device (e.g.portable computing device 400) usually consist in simulation datagenerated by the simulation functionalities 210 (e.g. 2D or 3D maps),and adapted by a particular instance of rendering function 240. Forexample, the aforementioned Navigation function of the server simulationfunctionalities 210 generates simulation data transmitted to aNavigation rendering function 240. The Navigation rendering function 240adapts the simulation data (e.g. a navigation map) for rendering on theportable computing device 400, and transmits the adapted simulation datato the portable computing device 400. Similarly, the aforementionedWeather function of the server simulation functionalities 210 generatessimulation data transmitted to a Weather rendering function 240. TheWeather rendering function 240 adapts the simulation data (e.g. aweather map) for rendering on the portable computing device 400, andtransmits the adapted simulation data to the portable computing device400. A plurality of instances of rendering function 240 (e.g. Navigationand Weather rendering functions) can be simultaneously generating andtransmitting adapted simulation data to the portable computing device400. The display function 421 of the portable computing device IOS UI420 receives and displays the simulation data which have been adaptedand transmitted by the Navigation and Weather rendering functions 240.

The web server function 250 directly transmits data to the portablecomputing device 400, which do not need to be processed by one of theinstances of rendering function 240. Such data usually include the IOScontrol and monitoring data 222 (e.g. a control web page) generated bythe server IOS functionality 220, which are transmitted to the webserver function 250, and further transmitted to the portable computingdevice 400. Such data may also include complementary simulation datagenerated by one of the server simulation functionalities 210. Forinstance, the Navigation function of the server simulationfunctionalities 210 generates complementary simulation data (e.g.parameters of the simulation such as wind speed, events of thesimulation such as aircraft speed too high, etc.), which are transmittedto the web server function 250, and further transmitted to the portablecomputing device 400. The parameters and/or events can be displayed onthe display 404 of the portable computing device 400 in the form oficons, text fields, etc. For instance, the parameters and/or eventsconstitute additional simulation information displayed in complement ofa Navigation map displayed on the display 404 of the portable computingdevice 400. The Navigation map has been generated by the Navigationrendering function 240 based on simulation data generated by theNavigation function of the server simulation functionalities 210, andtransmitted to the portable computing device 400.

For example, the IOS function IOS_1 of the server IOS functionality 220transmits IOS control and monitoring data 222 (e.g. a Navigation controlweb page) to the portable computing device 400 for controlling theexecution of the Navigation function of the server simulationfunctionalities 210. The IOS control and monitoring data 222 aretransmitted by the IOS function IOS_1 to the web server function 250,and further transmitted to the portable computing device 400 fordisplay. The IOS control and monitoring data 222 are displayed by thedisplay function 421 of the portable computing device IOS UI 420 on thedisplay 404. User 10 interacts with the displayed IOS control andmonitoring data 222 (e.g. the Navigation control web page) and theinteraction function 422 of the portable computing device IOS UI 420generates IOS interaction data 222. User 10 interacts via the userinterface 405 (e.g. a keyboard, a mouse, a trackpad, a touch screen,etc.) of the portable computing device 400, and the IOS interaction data222 are generated based on this interaction. The IOS interaction data222 are transmitted by the portable computing device 400 to the webserver function 250, and forwarded to the IOS function IOS_1. The IOSfunction IOS_1 processes the IOS interaction data 222 and controls theexecution of the Navigation function of the server simulationfunctionalities 210 based on the processed IOS interaction data 222.

Simultaneously, the IOS function IOS_2 of the server IOS functionality220 transmits IOS control and monitoring data 222 (e.g. a Weathercontrol web page) to the portable computing device 400 for controllingthe execution of the Weather function of the server simulationfunctionalities 210. The IOS control and monitoring data 222 aretransmitted by the IOS function IOS_2 to the web server function 250,and further transmitted to the portable computing device 400 fordisplay. The IOS control and monitoring data 222 are displayed by thedisplay function 421 of the portable computer device IOS UI 420 on thedisplay 404. User 10 interacts with the displayed control data (e.g. theWeather control web page) and the interaction function 422 of theportable computing device IOS UI 420 generates IOS interaction data 222.The IOS interaction data 222 are transmitted by the portable computingdevice 400 to the web server function 250, and forwarded to the IOSfunction IOS_2. The IOS function IOS_2 processes the IOS interactiondata 222 and controls the execution of the Weather function of theserver simulation functionalities 210 based on the processed IOSinteraction data 222.

In a particular embodiment, a visual database (not shown in the Figures)may be used on the simulation server 200. The visual database containsdata (e.g. terrain, buildings, 3D models, etc.) that can be streamed anddisplayed on the portable computing device 400, via one or moreinstances of rendering function 240. The visual database also containsparameters and/or events that can be overlaid on the displayed data,after direct transmission to the portable computing device 400 via theweb server function 250.

Referring now simultaneously to FIGS. 3A and 4, FIG. 4 illustrates asingle simulation server 200 supporting a plurality of simulators (e.g.300 and 300′), and a plurality of computing devices (e.g. 400 and 400′).Although two simulators have been represented in FIG. 4, the simulationserver 200 may support any number of simulators, based on its processingand communication capabilities. Similarly, although two portablecomputing devices have been represented in FIG. 4, the simulation server200 may support any number of portable computing devices, based on itsprocessing and communication capabilities.

For illustration purposes, the simulation server 200 executes a firstsimulation and a first user (a trainee in this particular instance)interacts with the first simulation via the simulator 300, while asecond user (an instructor in this particular instance) interacts withthe first simulation via the portable computing device 400.Simultaneously, the simulation server 200 executes a second simulationand a third user (another trainee) interacts with the second simulationvia the simulator 300′, while a fourth user (a second instructor)interacts with the second simulation via the portable computing device400′.

For illustration purposes, the server simulation functionalities 210 ofthe simulation server 200 execute simultaneously a first instance ofWeather function in relation to the first simulation, and a secondinstance of Weather function in relation to the second simulation. Eachinstance of Weather function generates simulation data (e.g. a weathermap), which are respectively transmitted directly to the simulators 300and 300′, via the web server function 250, without using a renderingfunction 240. Although two instances of Weather function are mentionedin this example, a larger number of instances can be operatingsimultaneously on the simulation server 200.

For illustration purposes, the rendering functions 240 executesimultaneously a first instance of Weather rendering function inrelation to the first simulation, and a second instance of Weatherrendering function in relation to the second simulation. Each instanceof Weather function executed by the server simulation functionalities210 generates simulation data (e.g. the weather map), which arerespectively adapted by the instances of Weather rendering function,before transmission to the portable computing devices 400 and 400′.Although two instances of Weather rendering function are mentioned inthis example, a larger number of instances can be operatingsimultaneously on the simulation server 200. The adapted simulation datatransmitted to the portable computing devices 400 and 400′ may differ,based on specific characteristics of each of the portable computingdevices 400 and 400′. For instance, a Weather map with a betterresolution may be generated for the portable computing devices 400 thanfor the portable computing device 400′.

For illustration purposes, the server IOS functionality 220 executessimultaneously a first and a second instance of the IOS function IOS_2for respectively controlling the first and second instances of Weatherfunction executed by the server simulation functionalities 210. Thefirst instance of IOS function IOS_2 transmits IOS control andmonitoring data 222 (e.g. a Weather control web page) to the portablecomputing device 400 for controlling the execution of the first instanceof Weather function. The control data are transmitted by the firstinstance of IOS function IOS_2 to the web server function 250, andfurther transmitted to the portable computing device 400 for display.IOS Interaction data 222 are generated and transmitted by the portablecomputing device 400 to the web server function 250, and forwarded tothe first instance of IOS function IOS_2. The first instance of IOSfunction IOS_2 processes the IOS interaction data 222 and controls theexecution of the first instance of Weather function executed by theserver simulation functionalities 210, based on the processed IOSinteraction data 222.

The second instance of IOS function IOS_2 transmits IOS control andmonitoring data 222 (e.g. a Weather control web page) to the portablecomputing device 400′ for controlling the execution of the secondinstance of Weather function executed by the server simulationfunctionalities 210. The control data are transmitted by the secondinstance of IOS function IOS_2 to the web server function 250, andfurther transmitted to the portable computing device 400′ for display.IOS Interaction data 222 are generated and transmitted by the portablecomputing device 400′ to the web server function 250, and forwarded tothe second instance of IOS function IOS_2. The second instance of IOSfunction IOS_2 processes the IOS interaction data 222 and controls theexecution of the second instance of Weather function executed by theserver simulation functionalities 210, based on the processed IOSinteraction data 222. Although two instances of IOS function IOS_2 arementioned in this example, a larger number of instances can be operatingsimultaneously on the simulation server 200.

Alternatively, the server simulation functionalities 210 may executesimultaneously an instance of Weather function in relation to the firstsimulation, and an instance of Navigation function in relation to thesecond simulation. Each instance of Weather and Navigation functionexecuted by the server simulation functionalities 210 generatessimulation data (e.g. a weather map and a navigation map), which arerespectively transmitted directly to the simulators 300 and 300′, viathe web server function 250. The rendering functions 240 executesimultaneously an instance of Weather rendering function in relation tothe first simulation, and an instance of Navigation rendering functionin relation to the second simulation. Each instance of Weather andNavigation function executed by the server simulation functionalities210 generates simulation data (e.g. the weather map and the navigationmap), which are respectively adapted by the instances of Weather andNavigation rendering function, before transmission to the portablecomputing devices 400 and 400′.

In this case, the server IOS functionality 220 executes simultaneouslyan instance of IOS function IOS_1 and an instance of IOS function IOS_2,for respectively controlling the instances of Navigation and Weatherfunction executed by the server simulation functionalities 210. Theinstances of IOS function IOS_1 and IOS function IOS_2 operate aspreviously described with respect to the portable computing devices 400and 400′.

In a similar manner, the server GUI functionality 230 executessimultaneously a first instance of the server GUI functionality 230 inrelation to the first simulation, and a second instance of the serverGUI functionality 230 in relation to the second simulation. Eachinstance of the server GUI functionality 230 generates GUI graphicaldata 232, which are respectively transmitted to the simulators 300 and300′, via the web server function 250. Each instance of server GUIfunctionality 230 also receives, via the web server function 250, GUIinteraction data 232 which are respectively transmitted by thesimulators 300 and 300′. The simulator GUI 330 displays the GUIgraphical data 232 received from the simulation server 200 on thesimulators 300 and 300′, and generates the GUI interaction data 232based on the interactions of the users 20 with the displayed GUIgraphical data 232. Each instance of the server GUI functionality 230 onthe simulation server 200 processes the GUI interaction data 232transmitted by the simulators 300 and 300′, and respectively controlsthe execution of the first and second instance of the simulation, basedon the processed GUI interaction data 232. Simulation data generated bythe server simulation functionalities 210 are also transmitted directlyby the web server function 250 (without adaptation by a renderingfunction 240) to the simulators 300 and 300′, for display by thesimulator GUI 330.

In an alternative embodiment, the web server function 250 is executed bya dedicated processing unit of the simulation server 200 (notrepresented in the Figures) different from the processing unit 201.

In another alternative embodiment, several instances of the web serverfunction 250 are executed by the processing unit 201. For example, aninstance is dedicated to the server IOS functionality 220, an instanceis dedicated to the server simulation functionalities 210 and aninstance is dedicated to the server GUI functionality 230. As mentionedpreviously, at least some of the instances may be executed by adedicated processing unit different from the processing unit 201.

In still another alternative embodiment, the web server function 250 isnot implemented on the simulation server 200, but on a standalone servernot represented in the Figures.

Reference is now made concurrently to FIGS. 3A, 3B, 3C, 6A, 6B and 6C,where FIGS. 6A, 6B and 6C represent an exemplary flow diagram 600illustrating interactions between the portable computing device 400 andcomponents of the simulation server 200. More precisely, this exemplaryflow diagram 600 illustrates interactions of the portable computingdevice IOS UI 420 with the simulation server 200.

At step 610, the user of the portable computing device 400 performs anauthentication by entering its credentials, and the portable computingdevice web client function 450 transmits the credentials to the webserver function 250. The web server function 250 verifies if the user isauthorized to connect to the simulation portal based on the usercredentials, and grants/denies access to the simulation portal based onthe result of the verification of the user credentials. This step isoptional, but is usually implemented to avoid that any user is grantedaccess to the simulation portal without restrictions. An administratorof the simulation portal may be granted access to managementfunctionalities of the portal, while standard users generally only haveaccess to simulation functionalities of the portal.

At step 615, the portable computing device web client function 450initiates a simulation web session with the web server function 250. Forexample, the user of the portable computing device 400 enters a UniformResource Locator (URL) corresponding to a simulation portal hosted bythe web server function 250, and the portable computer device web clientfunction 450 requests a connection to the simulation server 200,hereinafter referred as the simulation portal. In return, the web serverfunction 250 returns a home page of the simulation portal to bedisplayed by the portable computing device web client function 450.

At step 620, the web server function 250 transmits a list of candidateserver simulation functionalities 210 (e.g. Weather function, Navigationfunction, etc.) to the portable computing device web client function450. The list may be determined based on a particular profile of theuser, and may comprise only a subset (e.g. Weather function only) of allavailable server simulation functionalities 210 supported by the webserver function 250. The subset corresponds to server simulationfunctionalities 210 (e.g. Weather function only) that the user of theportable computing device 400 is authorized to use based on its profile.For each user, the web server function 250 stores a profile of the userfor determining the corresponding authorized server simulationfunctionalities 210. The profile of each user can be generated by anadministrator of the web server function 250. For example, in the caseof an aircraft simulation, the user may only be authorized to use serversimulation functionalities 210 corresponding to one or more particulartype(s) of aircraft, to one or more particular system(s) orsub-system(s) of an aircraft, to military or civilian aircrafts only,etc. The portable computing device web client function 450 displays thelist of candidate server simulation functionalities 210 (e.g. Weatherfunction and Navigation function) for allowing the user to select oneamong the list of candidates. The selection of a particular serversimulation functionality (e.g. Weather function) in the list ofcandidate server simulation functionalities 210 by the user istransmitted to the web server function 250 function by the portablecomputing device web client function 450. Alternatively, a plurality ofcandidate server simulation functionalities 210 can be selectedsimultaneously.

At step 621, the web server function 250 determines if an instance ofthe selected server simulation functionality 210 (e.g. Weather function)is already running, and if it is not the case, launches such aninstance. Since the simulation server 200 can support a plurality ofsimulation sessions in parallel, a server simulation functionality 210(e.g. Weather function) may have several instances running in parallelfor different independent simulation sessions. Thus, before executingstep 620, the user may need to join an existing simulation session orcreate a new simulation session. The creation of/joining to a simulationsession is performed through interactions between the portable computingdevice web client function 450 and the web server function 250. Eachindependent simulation session is allocated a unique identifier andinformation describing the characteristics of the simulation session, sothat any portable computing device 400 or simulator 300 can join theproper ongoing simulation session based on its characteristics (e.g.type of aircraft simulated, simulator 300 used for the simulation,etc.).

The selected server simulation functionality 210 (e.g. Weather function)may automatically provide access to corresponding IOS function(s) of theserver IOS functionality 220 (e.g. IOS function IOS_2). Alternatively,an interactive selection step 622 similar to selection step 620 isperformed. At step 622, the web server function 250 transmits a list ofcandidate IOS function(s) of the server IOS functionality 220 (e.g. IOSfunction IOS_1, IOS function IOS_2, etc.) to the portable computingdevice web client function 450. The list may be determined based on aparticular profile of the user, and may comprise only a subset (e.g. IOSfunction IOS_2 only) of all available server IOS functions supported bythe web server function 250. The subset corresponds to server IOSfunctions 220 (e.g. IOS function IOS_2 only) that the user of theportable computing device 400 is authorized to use based on its profile.For each potential user, the web server function 250 stores a profile ofthe user for determining the corresponding authorized server IOSfunctions 220. The portable computing device web client function 450displays the list of candidate server IOS functions 220 (e.g. IOSfunction IOS_1 and IOS function IOS_2) for allowing the user to selectone among the list of candidates. The selection of server IOS functions220 (e.g. IOS function IOS_2) in the list of candidate server IOSfunctions by the user is transmitted to the web server function 250 bythe portable computing device web client function 450. Alternatively, aplurality of candidate server IOS functions 220 can be selectedsimultaneously.

At step 625, the web server function 250 launches an instance of serverIOS function 220 corresponding to the IOS function (e.g. IOS_2) selectedat step 622. The web server function 250 also launches an instance ofserver rendering function 240 (e.g. Weather rendering function)corresponding to the server simulation functionality 210 (e.g. Weatherfunction) selected at step 620. As mentioned previously, severalinstances of the same server IOS function 210 or server renderingfunction 240 can be executed in parallel by the simulation server 200,for supporting a plurality of simulation sessions running in parallel,and also for supporting a plurality of portable computing devices 400participating in parallel to the same or similar simulation sessions.Furthermore, a single portable computing device 400 may be interactingwith a plurality of server IOS functions 210 and/or a plurality ofserver rendering functions 240 in parallel.

The web server function 250 establishes a first communication channelfor exchanging data between the portable computing device 400 and theinstance of server IOS function 220 (e.g. IOS function IOS_2) launchedat step 625; and optionally between the portable computing device 400and the instance of server simulation functionality 210 (e.g. Weatherfunction) launched at step 621 (to directly transmit simulation datawhich do not need to be adapted by a rendering function). The data areexchanged between the simulation server 200 and the portable computingdevice 400 through the web server function 250 and the portablecomputing device web client 450. All the data exchanged through thisfirst communication channel do not need to be adapted for rendering onthe portable computing device 400 via a server rendering function 240.

The web server function 250 establishes a second communication channelbetween the instance of server rendering function 240 (e.g. Weatherrendering function) launched at step 625 and the portable computingdevice 400, for transmitting simulation data adapted for rendering onthe portable computing device 400. Establishing this secondcommunication channel is well known in the art, and may comprisedetermining a connection identification, selecting communicationprotocol(s), allocating communication sockets, etc.

The web server function 250 may create and manage a dynamiccommunication profile for each portable computing device 400, comprisingcharacteristics of the created first and second communication channels.The management of the dynamic communication profile includescreation/update/deletion of the first and second communication channels.

Furthermore, the web server function 250 provides the launched instanceof server rendering function 240 with characteristics of the portablecomputing device 400. The characteristics include for example processingpower, memory size, display resolution, data throughput of acommunication interface, available user interfaces, etc. Thesecharacteristics are used by the launched instance of server renderingfunction 240 for performing the adaptation of the simulation datatransmitted to the portable computing device 400. For each authorizeduser of the simulation portal, the web server function 250 may store astatic profile (with the aforementioned characteristics) of the portablecomputing device 400 used by the user. Alternatively, the web serverfunction 250 automatically generates a dynamic profile (with theaforementioned characteristics) of the portable computing device 400used by the user at step 610, by dynamically retrieving thecharacteristics of the device 400 currently used by the user (thisprocedure is well known in the art of web browsing).

FIG. 6B more specifically represents the transmission of adaptedsimulation data by the instance of server rendering function 240 to theportable computing device 400.

At step 630, the instance of server simulation functionality 210 (e.g.Weather function) generates simulation data and forwards the simulationdata to the corresponding instance of server rendering function 240(e.g. Weather rendering function).

At step 635, the instance of server rendering function 240 processes thesimulation data, and generates simulation data adapted (based on theaforementioned characteristics of the portable computing device 400) forrendering on the portable computing device 400.

At step 640, the adapted simulation data are transmitted directly by theinstance of server rendering function 240 to the portable computingdevice 400 (without using the web server function 250).

At step 645, the display function 421 of the portable computing deviceIOS UI 420 processes the adapted simulation data received from theinstance of server rendering function 240, and displays the processedsimulation data on the display 404 of the portable computing device 400.Since the simulation data have been adapted to the device 400 at step635, the processing is very limited and may even not be needed beforedisplaying the simulation data.

Although a single sequence of steps 630, 635, 640 and 645 is representedin FIG. 6B for simplification purposes, a plurality of sequences mayoccur. For each sequence, simulation data adapted for rendering on theportable computing device 400 are generated at steps 630 and 635,transmitted at step 640 and displayed at step 645.

FIG. 6C more specifically represents the exchange of data not adapted bya server rendering function 240 between the web server function 250 andthe portable computing device 400.

At step 650, the instance of server IOS function 220 (e.g. IOS_2)generates IOS control and monitoring data 222 (not adapted by arendering function), and forwards the IOS control and monitoring data222 to the web server function 250.

At step 655, the IOS control and monitoring data 222 are transmitted bythe web server function 250 to the portable computing device 400(without applying any rendering function).

At step 660, the display function 421 of the portable computing deviceIOS UI 420 displays the received IOS control and monitoring data 222 onthe display 404 of the portable computing device 400.

At step 665, the interaction function 422 of the portable computingdevice IOS UI 420 generates IOS interaction data 222 based oninteractions of the user of the portable computing device 400 (e.g. withthe IOS control and monitoring data 222 displayed at step 660).

At step 670, the IOS interaction data 222 are transmitted by theportable computing device 400 to the web server function 250. The webserver function 250 simply forwards the IOS interaction data 222 to theinstance of server IOS function 220 (e.g. IOS_2).

The web server function 250 may implement a filtering function (notrepresented in the Figures), for identifying and adequately handling thedata received from the portable computing device(s) 400. The filteringfunction identifies IOS interaction data 222 received at step 670, whichshall be forwarded to the proper instance of server IOS function 220(e.g. IOS_2). The filtering function also identifies administrative andmanagement data received at steps 610, 615, 620 and 622 of FIG. 6A,which shall be processed directly by the web server function 250.

At step 675, the instance of server IOS function 220 (e.g. IOS_2)processes the IOS interaction data 222 to control the execution of thesimulation executed by the simulation server 200 based on the IOSinteraction data 222.

Although a single sequence of steps 650, 655 and 660 is represented inFIG. 6C for simplification purposes, a plurality of sequences may occur.Similarly, a plurality of sequences of steps 665, 670 and 675 may occur.A plurality of sequences of steps 650, 655 and 660 may occur before asingle sequence of steps 665, 670 and 675 occurs. Similarly, a pluralityof sequences of steps 665, 670 and 675 may occur before a singlesequence of steps 650, 655 and 660 occurs. However, a sequence of steps665, 670 and 675 is generally followed by a sequence of steps 650, 655and 660 (and/or steps 630, 635, 640 and 645 of FIG. 6B); since theprocessing of the IOS interaction data 222 impacts the execution of thesimulation executed by the simulation server 200, which in turn leads tothe generation of new adapted simulation data 212/IOS control andmonitoring data 222 which are transmitted to the portable computingdevice 400.

Although not represented in FIG. 6C for simplification purposes, steps650, 655 and 660 may also consist in the generation by the instance ofserver simulation functionality 210 represented in FIG. 6B of simulationdata which do not need to be adapted by a rendering function, thetransmission of these simulation data to the portable computing device400 directly by the web server function 250, and the display of thesesimulation data on the portable computing device 400

Furthermore, the transmission of simulation data adapted by the instanceof server rendering function 240 as illustrated in FIG. 6B, and thetransmission of IOS control and monitoring data 222/simulation data 212by the web server function 250 (without adaptation by a renderingfunction) as illustrated in FIG. 6C, occur simultaneously andindependently.

As is well known in the art, the communications between the web serverfunction 250 and the portable computing device web client 450 use theHypertext Transfer Protocol (HTTP) and/or Hypertext Transfer ProtocolSecure (HTTPS). Optionally, the Real-time Transport Protocol (RTP) mayalso be used for some of the data exchanged between the web serverfunction 250 and portable computing device(s) 400. A single steprepresented in FIGS. 6A and 6C (e.g. 610, 615, 620, 622, 655 and 670)may include a plurality of HTTP/HTTPS/RTP messages exchanged between theweb server function 250 and portable computing device(s) 400.

Similarly, the communications between the instances of server renderingfunction 240 and portable computing device(s) 400 may also use the HTTPand/or HTTPS and/or RTP protocols. A single step represented in FIG. 6B(e.g. 640) may include a plurality of HTTP/HTTPS/RTP messages exchangedbetween the instances of server rendering function 240 and portablecomputing device(s) 200. In this case, each instance of server renderingfunction 240 implements an autonomous HTTP based server allowingcommunications with the portable computing device(s) 400 via websockets. The establishment of the communication channel between theinstances of server rendering function 240 and portable computingdevice(s) 400 is performed under the direction of the web serverfunction 250 at step 625. However, this communication channel is notlimited to the use of the HTTP and/or HTTPS and/or RTP protocols, butmay use other non-web-based communication protocols (e.g. a proprietarycommunication protocol).

The flow diagram 600 is for illustration purposes only. A similar flowdiagram may be adapted to illustrate interactions of the portablecomputing device GUI 430 represented in FIG. 2B, with the simulationserver 200. Additionally, similar flow diagrams may be respectivelyadapted to illustrate interactions of the simulator IOS UI 320,simulator GUI 330 and simulator simulation functionalities 310 executedon the simulator 300 represented in FIG. 2A, with the simulation server200.

Reference is now made concurrently to FIGS. 3A, 3B, 3C and 5. FIG. 5represents an IOS UI page 500 displayed on the display 304 of thesimulator 300. The IOS UI page 500 is displayed by the display function321 of the simulator IOS UI 320. The IOS UI page 500 provides a userinterface with sub-groups of instances. The IOS UI page 500 generallyincludes graphical control elements (e.g. menus and sub-menus, listboxes, etc.) for controlling simulation parameters, and graphicaldisplay elements (e.g. images, text fields, icons, embedded videos,etc.) for displaying simulation data generated by the server simulationfunctionalities 210.

The IOS UI page 500 represented in FIG. 5 comprises a first image 501(Navigation map), a graphical control element 502 (control widget), anda second image 503 (Weather map). The Navigation map is generated by theNavigation function of the server simulation functionalities 210, anddirectly transmitted (without adaptation by the server renderingfunction 240) to the simulator IOS UI 320 via the web server function250, for display on the simulator display 304 by the simulator displayfunction 321. The Navigation map is updated based on the execution ofthe Navigation function of the server simulation functionalities 210.The Weather map 503 is generated by the Weather function of the serversimulation functionalities 210, and directly transmitted (withoutadaptation by the server rendering function 240) to the simulator IOS UI320 via the web server function 250, for display on the simulatordisplay 304 by the simulator display function 321. The Weather map isupdated based on the execution of the Weather function of the serversimulation functionalities 210.

The web server function 250 receives IOS control and monitoring data 222corresponding to the control widget 502 (allowing control of theNavigation map 501 and Weather map 503) from the server IOSfunctionality 220. The IOS control and monitoring data 222 aretransmitted to the simulator 300 by the web server function 250, and thecontrol widget 502 is displayed on the simulator display 304 by thesimulator display function 321 of the simulator IOS UI 321 based on thereceived IOS control and monitoring data 222. The control widget 502 isused by a user for modifying parameters related to the Navigation map501 and the Weather map 503, when the user interacts with the simulator300 via the interaction function 322 of the simulator IOS UI 320. IOSInteraction data 222 comprising the modified parameters are transmittedby the interaction function 322 of the simulator IOS UI 320 to theserver IOS functionality 220, for controlling the execution of theNavigation and Weather functions of the server simulationfunctionalities 210.

FIG. 5 also represents an IOS UI page 510 displayed on the display 404of the portable computing device 400. The IOS UI page 510 is displayedby the portable computing device display function 421 of the portablecomputing device IOS UI 420. The IOS UI page 510 comprises an image 511(Navigation map) corresponding to the Navigation map 501 of the IOS UIpage 500, and a graphical control element 512 (control widget)corresponding to the control widget 502 of the IOS UI page 500.

For illustration purposes, the user of the portable computing device 400has decided not to use the Weather function of the server simulationfunctionalities 210, and consequently an image corresponding to theWeather map 503 of the IOS UI page 500 is not displayed on the display404 of the portable computing device 400. In an alternative use case notrepresented in FIG. 5, if the user of the portable computing device 400had decided to use the Weather function of the server simulationfunctionalities 210, an image corresponding to the Weather map 503 ofthe IOS UI page 500 would be displayed on the portable computing devicedisplay 404.

On the simulation server 200, an instance of Navigation renderingfunction 240 receives simulation data corresponding to the Navigationmap 511 from the Navigation function of the server simulationfunctionalities 210. The instance of Navigation rendering function 240processes the simulation data to generate the Navigation map 511 adaptedfor rendering on the portable computing device 400. For example, thesize and resolution of the Navigation map 511 is adapted tocharacteristics (e.g. screen resolution, etc.) of the portable computingdevice 400. The Navigation map 511 is transmitted to the portablecomputing device 400 by the instance of server rendering function 240,and displayed on the portable computing device display 404 by theportable computer device IOS UI 421.

The web server function 250 at the simulation server 200 receives IOScontrol and monitoring data 222 corresponding to the control widget 512(allowing control of the Navigation map 511) from the server IOSfunctionality 220. The IOS control and monitoring data 222 aretransmitted to the portable computing device 400 by the web serverfunction 250, and the control widget 512 is displayed on the portablecomputing device display 404 by the portable computing device IOS UI 421based on the received IOS control and monitoring data 222.

When the user 10 interacts with the IOS UI page 510 via a user interface405 of the portable computing device 400, corresponding IOS interactiondata 222 are generated by the interaction function 422 of the portablecomputing device IOS UI 420, and transmitted by the interaction function422 to the web server function 250 of the simulation server 200. The webserver function 250 forwards the IOS interaction data 222 to the serverIOS functionality 220.

For example, the control widget 512 is a menu comprising three items.When the user positions a pointer (corresponding to a mouse) on one ofthe items and left clicks, the transmitted IOS interaction data 222comprise the selected item.

Alternatively or complementarity, the user 10 may interact directly withan area of the IOS UI page 510 without using the control widget 512. Forexample, the user 10 may position a pointer (corresponding to a mouse)on the Navigation map 511, and left click or right click on theNavigation map 511. The transmitted IOS interaction data 222 comprise anindication that the user 10 interacted with the Navigation map 511, andmore specifically via a right-click or a left-click. The IOS interactiondata 222 are interpreted by the server IOS functionality 220 at thesimulation server 200 as follows: a left-click is a zoom-in request anda right-click is a zoom-out request. The server IOS functionality 220reconfigures the Navigation function of the server simulationfunctionalities 210 accordingly. In case of a zoom-in, the Navigationfunction of the server simulation functionalities 210 generates moredetailed simulation data, which are processed by the instance ofNavigation server rendering function 240 for generating a zoomed-inNavigation map 511 for rendering on the portable computing device 400.In case of a zoom-out, the Navigation function of the server simulationfunctionalities 210 generates less detailed simulation data, which areprocessed by the instance of Navigation server rendering function 240for generating a zoomed-out Navigation map 511 for rendering on theportable computing device 400.

More generally, the IOS interaction data 222 are used by the server IOSfunctionality 220 for controlling the corresponding server simulationfunctionality 210 (e.g. Navigation function). Controlling thecorresponding server simulation functionality 210 includes controllingthe simulation data generated by the server simulation functionality 210(e.g. Navigation function), which are further adapted by thecorresponding instance of server rendering function 240 (e.g. instanceof Navigation server rendering function 240) for rendering (e.g.Navigation map 511) on the portable computing device display 404.

The web server function 250 may pre-process the received IOS interactiondata 222 to determine if they correspond to a legitimate interactionwith the IOS UI page 510 displayed on the portable computing device 400.The web server function 250 simply discards transmitted IOS interactiondata 222 which do not correspond to a legitimate interaction with theIOS UI page 500, and transmits legitimate interactions to the server IOSfunctionality 220. The web server function 250 may further discriminatethe IOS interaction data 222 generated with the IOS UI page 510, fromother types of data (e.g. administration and configuration of thesimulation server 200) which are processed directly by the web serverfunction 250.

Transmission of IOS Filtered Information

Referring now concurrently to FIGS. 7A, 7B, 7C, 7D, 8 and 9, atransmission of IOS filtered information from a portable computingdevice to a destination computing device is illustrated. The filteringof the IOS information is based on user access rights of a user who isthe destination of the transferred IOS filtered information.

Referring more specifically to FIGS. 7A, 8 and 9, the entitiesrepresented in FIG. 7A are the same as the entities represented in FIG.2B (which have already been described in details), and the portablecomputing device 400 represented in FIG. 8 corresponds to the portablecomputing device 400 represented in FIG. 3C (which has already beendescribed in details) with additional functionalities for generating theIOS filtered information to be transmitted. FIG. 9 represents a method700 for transmitting IOS filtered information, which can be implementedby the portable computing device 400 represented in FIG. 8.

At step 705 of the method 700, the processing unit 401 of the portablecomputing device 400 receives IOS control and monitoring data 222 fromthe simulation server 200 via the communication interface 403 of theportable computing device 400. The IOS control and monitoring data 222are generated and transmitted by the server IOS functionality 220 of thesimulation server 200.

At step 710 of the method 700, the processing unit 401 displays the IOScontrol and monitoring data 222 on the display 404 of the portablecomputing device 400. The display is performed by the display function421 of the portable computing device IOS UI 420 executed by theprocessing unit 401. FIG. 10A illustrates an example where the IOScontrol and monitoring data 222 consist in an IOS UI page 800 displayedon the display 404.

As described previously in details, the processing unit 401 generatesIOS interaction data 222, which are transmitted to the simulation server200 via the via the communication interface 403. The transmitted IOSinteraction data 222 are further processed by the server IOSfunctionality 220 of the simulation server 200, to control the executionof a simulation by the simulation server 200. The transmitted IOSinteraction data 222 correspond to interactions of the user 10 with theIOS control and monitoring data displayed on the display 404 via theuser interface 405 of the portable computing device 400. The generationand transmission of the IOS interaction data 222 is performed by theinteraction function 422 of the portable computing device IOS UI 420executed by the processing unit 401.

The interactions of the user 10 with the user interface 405 are notlimited to the generation of the IOS interaction data 222. According tostep 715 of the method 700, the processing unit 401 may also receive aselection by the user 10 of at least one component of the IOS controland monitoring data displayed on the display 404, for the purpose ofgenerating IOS filtered information. The selection corresponds to aninteraction of the user 10 with the user interface 405, and thereception of the selection can be performed by the interaction function422 of the portable computing device IOS UI 420.

At step 720 of the method 700, the processing unit 401 determines IOSfiltered information related to the selected at least one component. Thedetermination takes into consideration destination user access rights ofa destination user 20. The destination user 20 is a user currentlyperforming a simulation session on a destination computing device, suchas the portable computing device 400′ represented in FIG. 7A. Thedestination user access rights are used to determine which IOSinformation related to the selected at least one component can be sharedwith the destination user 20.

The determination can be performed in two steps. In a first step, IOSinformation logically related to the selected at least one component aredetermined. In this first step, the determination is based on theintrinsic structure/hierarchy of the displayed IOS control andmonitoring data 222, to identify which IOS information is logicallyrelated to the selected at least one component. However, not all the IOSinformation determined in this first step may be shared with thedestination user 20, based on its particular user access rights. Thus,in a second step, IOS filtered information are determined based on theIOS information identified at the first step, and further based on thedestination user access rights. The IOS filtered information consists ina subset of the IOS information related to the selected at least onecomponent determined at the first step, the subset being determinedbased on the destination user access rights.

The determination of the IOS filtered information can be performed by adedicated functionality (the filtering function 423 represented in FIG.8) of the portable computing device IOS UI 420 executed by theprocessing unit 401. The destination user access rights are stored inthe memory 402 of the portable computing device 400, as will be detailedlater in the description.

At step 725 of the method 700, the processing unit 401 transmits the IOSfiltered information 224 to the destination computing device via thecommunication interface 403. In the particular embodiment illustrated inFIG. 7A, the destination computing device is the portable computingdevice 400′, which is capable of displaying the IOS filtered information224 on a display of the destination portable computing device 400′. Asmentioned previously in the description, the portable computing deviceGUI 430 executed by the portable computing device 400′ displays GUIgraphical data 232 (and optionally simulation data 212), received fromthe simulation server 200, on the display of the portable computingdevice 400′. The IOS filtered information 224 can also be displayed bythe portable computing device GUI 430, and may be integrated with thedisplayed GUI graphical data 232 (and optionally simulation data 212).The display of the IOS filtered information 224 will be detailed laterin the description, in relation to FIGS. 10A and 10B.

In a particular aspect, the user 10 is an instructor controlling andmonitoring the execution of a simulation executed by the simulationserver 200, and further controlling and monitoring the interactions of atrainee 20 with the simulation. The IOS filtered information 224 sharedby the instructor 10 with the trainee 20 are usually not available tothe trainee 20. However, in particular circumstances, the instructor 10may share the IOS filtered information 224 with the trainee 20. Forinstance, if the trainee 20 fails to accurately perform a specificsimulation procedure (e.g. landing phase of an aircraft), the IOSfiltered information 224 may provide additional feedback, contextualdata, etc. to the trainee 20, in order to help him better understand thereasons of his failure. The IOS filtered information 224 are filteredbecause a trainee shall not have access to all the information availableto the instructor.

Referring more specifically to FIGS. 7B and 8, in the particularembodiment illustrated in FIG. 7B, the destination computing device isthe simulator 300, which is capable of displaying the IOS filteredinformation 224 on a display of the simulator 300. As mentionedpreviously in the description, the simulator GUI 330 executed by thesimulator 300 displays GUI graphical data 232 received from thesimulation server 200 on the display of the simulator 300. The IOSfiltered information 224 can also be displayed by the simulator GUI 330,and can be integrated with the displayed GUI graphical data 232.

Referring more specifically to FIGS. 7C and 8, in the particularembodiment illustrated in FIG. 7C, the destination computing device isthe simulator server 200. The simulation server 200 receives the IOSfiltered information 224, and forwards them to the portable computingdevice 400′. The display of the IOS filtered information 224 on thedisplay of the portable computing device 400′ has already been describedin relation to FIG. 7A. Although in FIG. 7C, the reception andforwarding of the IOS filtered information 224 is performed by theserver IOS functionality 220, the reception and/or forwarding may beperformed by another functionality of the simulation server 200 (e.g.reception by the server IOS functionality 220 and forwarding by theserver GUI functionality 230).

Referring more specifically to FIGS. 7D and 8, in the particularembodiment illustrated in FIG. 7D, the destination computing device isthe simulator server 200. The simulation server 200 receives the IOSfiltered information 224, and forwards them to the simulator 300. Thedisplay of the IOS filtered information 224 on the display of thesimulator 300 has already been described in relation to FIG. 7B.

In a particular aspect, the memory 402 of the portable computing device400 may store simulation session data, as illustrated in FIG. 8. Thesimulation session data include the destination user access rights usedfor determining the IOS filtered information 224 to be transmitted. Thesimulation session data also include an indication that the destinationuser 20 is currently performing a simulation session on the portablecomputing device 400′ (as illustrated in FIGS. 7A and 7C) or on thesimulator 300 (as illustrated in FIGS. 7B and 7D). As mentionedpreviously in the description, the execution of the simulation sessionon the portable computing device 400′ or on the simulator 300 iscontrolled through interactions of the user 10 with the IOS control andmonitoring data 222 displayed on the display 404 of the portablecomputing device 400, via the user interface 405 of the portablecomputing device 400. The simulation session data may be generated bythe server IOS functionality 220 of the simulation server 200, andtransmitted to the portable computing device 400 for storage in itsmemory 402. Updated simulation session data can be generated andtransmitted by the server IOS functionality 220, based on which user(s)20 are currently performing a simulation session on a portable computingdevice 400′ or simulator 300, the simulation session being supported bythe execution of a simulation on the simulation server 200. For thispurpose, the server IOS functionality 220 of the simulation server 200maintains a mapping between each specific user 10 controlling andmonitoring (via the portable computing device IOS UI 420 of the portablecomputing device 400) a simulation session performed by a specific user20 on a portable computing device 400′ or on a simulator 300, andbetween the corresponding specific user 20. Additionally, the simulationserver 200 stores the destination user access rights of all thedestination users 20 (e.g. trainees) who are allowed to perform asimulation session via the simulation server 200, under the supervisionof a user 10 (e.g. an instructor). The simulation session data may alsoinclude routing information allowing the transmission of the IOSfiltered information 224 to the destination portable computing device400′ or simulator 300 of the destination user 20. For instance, therouting information include the IP address of the destination portablecomputing device 400′ or simulator 300, a logical name of thedestination portable computing device 400′ or simulator 300 resolvablevia a Domain Name Server (DNS), etc.

In a particular aspect, the IOS control and monitoring data 222(received at step 705 and displayed at step 710 of the method 700)comprise one or more IOS User Interface (UI) pages, which will bereferred to as original IOS UI pages. IOS UI pages have already beendescribed previously.

The IOS filtered information (determined at step 720 of the method 700)comprises a subset of the one or more original IOS UI pages. Asmentioned in step 720, the subset is determined based on the destinationuser access rights. The IOS filtered information can be referred to asfiltered IOS UI page(s) consisting in the subset of the one or moreoriginal IOS UI pages.

Following is an example of how the filtered IOS UI page(s) may bedetermined. The selection (at step 715 of the method 700) of at leastone component of the displayed IOS control and monitoring data consistsin the selection of at least one component of the displayed one or moreoriginal IOS UI pages. A first subset of the one or more original IOS UIpages corresponding to the selected at least one component isdetermined. The correspondence between the selected at least onecomponent and the first subset of the one or more original IOS UI pagesis generally static, and is defined by the architecture of the one ormore original IOS UI pages. For example, upon selection of a particularcomponent of a specific IOS UI page among the one or more original IOSUI pages, the first subset of the one or more original IOS UI pages mayconsist in the specific IOS UI page only, or in the specific IOS UI pageand other original IOS UI page(s) hierarchically related to the specificIOS UI page. The first subset of the one or more original IOS UI pagesis further filtered based on the destination user access rights, toobtain the filtered IOS UI page(s). The filtering consists in excludingfrom the first subset particular IOS UI page(s) that the destinationuser is not allowed to visualize, as specified by its destination useraccess rights.

For each filtered IOS UI page (which corresponds to one of the originalIOS UI pages), the components of the filtered IOS UI page comprise asubset of the components of the corresponding original IOS UI page. Thesubset of components is also determined based on the destination useraccess rights. The subset of components can be referred to as thefiltered components of the filtered IOS UI page.

Following is an example of how the filtered components of the filteredIOS UI page may be determined. A first subset of components isdetermined from the original IOS UI page corresponding to the filteredIOS UI page. The first subset of components consists in components ofthe original IOS UI page which correspond to the selected at least onecomponent of step 715. As mentioned previously, the correspondencebetween the selected at least one component of step 715 and the firstsubset of component of the original IOS UI page is generally static, andis defined by the architecture of the original IOS UI page. All thecomponents of the original IOS UI page may be part of the first subset.Alternatively, only some of the components of the original IOS UI pagehierarchically related to the selected at least one component of step715 are part of the first subset. The first subset of components isfurther filtered based on the destination user access rights, to obtainthe final subset of filtered components. The filtering consists inexcluding from the first subset particular components that thedestination user is not allowed to visualize, as specified by itsdestination user access rights. The filtered components may includesub-components, which are also filtered based on the destination useraccess rights, in a similar manner as the components.

Reference is now made concurrently to FIGS. 7B, 8, 9, 10A and 10B. FIG.10A represents an IOS UI page 800 displayed on the display 404 of theportable computing device 400. The IOS UI page 800 is displayed by thedisplay function 421 of the portable computing device IOS UI 420. TheIOS UI page 800 generally includes graphical control elements (e.g.menus and sub-menus, list boxes, behavioral data, flight profile,events, metrics, training results, training assessment, etc.) forcontrolling simulation parameters, and graphical display elements (e.g.images, text and/or numerical fields, icons, embedded videos, etc.) fordisplaying simulation data generated and transmitted by the simulationserver 200.

The IOS UI page 800 represented in FIG. 10A comprises an image 801(Navigation map), graphical control elements 802 (control widgets), andlesson plan data 803. The generation of components 801, 802 and 803 ofthe IOS UI page 800 by the simulation server 200, the transmission ofthe components 801, 802 and 803 from the simulation server 200 to theportable computing device 400, and the display of the components 801,802 and 803 by the portable computing device 400, have already beendescribed in relation to the IOS UI page 500 represented in FIG. 5.

For illustration purposes, FIG. 10A corresponds to the embodimentsrepresented in FIGS. 7B and 7D, where IOS filtered information 224 aretransmitted (directly in FIG. 7B, and via the simulation server 200 inFIG. 7D) by the portable computing device IOS UI 420 to the simulatorGUI 330. The user 10 of the portable computing device 400 interacts withthe IOS UI page 800, while the user 20 of the simulator 300 interactswith a simulator GUI display 850 represented in FIG. 10A. However, thesubject matter recited in the following paragraphs can also be appliedto the embodiments represented in FIGS. 7A and 7C, where the user 10 ofthe portable computing device 400 interacts with the IOS UI page 800,while the user 20 of the portable computing device 400′ interacts with aportable computing device GUI display (displayed on the display of theportable computing device 400′) not represented in the Figures.

The simulator GUI display 850 represented in FIG. 10A is displayed onthe display 304 of the simulator 300. The simulator GUI display 850 isdisplayed by the simulator GUI functionality 330 represented in FIG. 3B.The simulator GUI display 850 comprises an image 851 (Navigation mapcorresponding to the Navigation map 801 of the IOS UI page 800),graphical control elements 852 (control widgets), and simulationparameters 853 (e.g. altitude of an aircraft, speed of an aircraft,etc.).

The user 10 of the portable computing device 400 interacts with thecontrol widgets 802 to select the lesson plan data 803, as per step 715of the method 700. The interaction also includes an indication that thelesson plan data 803 shall be transferred to the destination user 20currently performing a simulation session on the simulator 20. Afiltered IOS UI page corresponding to the IOS UI page 800 is generatedbased on the user access rights of the destination user 20, as per step720 of the method 700. The filtered IOS UI page comprises the filteredlesson plan data 855 and the filtered control widgets 856 represented in10B. The filtered lesson plan data 855 comprise a subset of theinformation of the lesson plan data 803, the subset consisting ininformation which can be shared with the destination user 20 accordingto its user access rights. The filtered control widgets 856 comprise asubset of the control widgets 802, the subset allowing the user 20 tonavigate through the filtered lesson plan data 855 in a similar manneras user 10 navigates through the lesson plan data 803 with the controlwidgets 802.

For example, the lesson plan data 803 include a plurality of simulationevents, and a plurality of simulation parameters which can be modifiedby the user 10 for controlling the execution of the simulation events bythe simulation server 200. Each simulation event includes an objective,a tolerance margin for the objective, and a result effectively achievedby the user 20. The plurality of simulation events may be defined as aplurality of IOS UI pages 800. For each particular simulation event, aparticular IOS UI page 800 comprising particular lesson plan data 803 isdisplayed. The particular lesson plan data 803 include the plurality ofsimulation parameters which can be modified by the user 10 (via thecontrol widgets 802) for controlling the execution of the particularsimulation event by the simulation server 200. The particular lessonplan data 803 also include the objective/tolerance margin/resulteffectively achieved by the user 20, with respect to the particularsimulation event.

If the results effectively achieved by the user 20 are not satisfying,the user 10 may decide to share some information with the user 20, tohelp him better understand why he failed. For this purpose, and asmentioned previously, the filtered lesson plan data 855 and the filteredcontrol widgets 856 are transmitted (as per step 725 of the method 700)from the portable computing device 400 to the simulator 300, and furtherdisplayed on the display 304 of the simulator 300 as illustrated in FIG.10B. The user access rights of the user 20 define, for each particularsimulation event, which information can be shared. For instance, onlythe objective, the result, and a subset of the simulation parameters,can be shared. The lesson plan data 803 containing all the simulationparameters, the objective, the tolerance margin, and the result arefiltered to generate the filtered lesson plan data 855 containing onlythe subset of the simulation parameters which can be shared, theobjective, and the result.

In a particular aspect, the IOS control and monitoring data displayed atstep 710 of the method 700 comprise a hierarchy of IOS UI pages, and theIOS filtered information determined at step 720 of the method 700comprises a subset of the hierarchy of IOS UI pages, the subset beingdetermined based on the destination user access rights. For example,upon selection of the lesson plan data 803 as per step 715 of the method700, a hierarchy of IOS UI pages (not represented in FIGS. 10A and 10B)logically related to the IOS UI page 800 (and more specificallylogically related to the lesson plan data 803 of the IOS UI page 800) isidentified. The hierarchy of identified IOS UI pages is further filteredbased on the destination user access rights, to generate the subset ofthe hierarchy of identified IOS UI pages which is transmitted to thedestination user 20.

In another aspect (referring to FIGS. 8 and 9), a non-transitorycomputer program product comprises instructions, which when executed bythe processing unit 401 of the portable computing device 400 implementthe method 700. More specifically, the execution of the instructionsimplements at least steps 705, 710, 715, 720 and 725 of the method 700represented in FIG. 9. The non-transitory computer program product mayconsist in the memory 402 of the portable computing device 400. Theinstructions are deliverable to the non-transitory computer programproduct via an electronically-readable media, such as storage media(e.g. a CD-ROM, a USB key, etc.) and communication links (e.g. thenetwork 30 via the communication interface 403 of the portable computingdevice 400).

Although the present disclosure has been described hereinabove by way ofnon-restrictive, illustrative embodiments thereof, these embodiments maybe modified at will within the scope of the appended claims withoutdeparting from the spirit and nature of the present disclosure.

What is claimed is:
 1. A portable computing device comprising: a display; a user interface for allowing interactions of a user with the portable computing device; a communication interface for exchanging data with other entities; a processing unit for: receiving Instructor Operating Station (IOS) control and monitoring data from a simulation server via the communication interface, the IOS control and monitoring data allowing the user of the portable computing device to control execution of a simulation in real-time; receiving simulation session data via the communication interface, the simulation session data comprising destination user access rights and an indication of a destination user that is currently executing the simulation; displaying the IOS control and monitoring data on the display; receiving a selection by the user of at least one component of the IOS control and monitoring data displayed on the display via the user interface; determining IOS filtered information as a subset of information related to the selected at least one component, the determination of the IOS filtered information taking into consideration the destination user access rights of the destination user currently executing the simulation; and transmitting the IOS filtered information to a destination computing device separate from the portable computing device via the communication interface.
 2. The portable computing device of claim 1, wherein the destination computing device is a destination portable computing device capable of displaying the IOS filtered information on a display of the destination portable computing device.
 3. The portable computing device of claim 2, wherein the destination user is currently executing the simulation on the destination portable computing device, the execution of the simulation on the destination portable computing device being controlled in real-time through interactions of the user with the IOS control and monitoring data displayed on the display via the user interface.
 4. The portable computing device of claim 1, wherein the destination computing device is a simulator capable of displaying the IOS filtered information on a display of the simulator.
 5. The portable computing device of claim 4, wherein the destination user is currently executing the simulation on the simulator, the execution of the simulation on the simulator being controlled in real-time through interactions of the user with the IOS control and monitoring data displayed on the display via the user interface.
 6. The portable computing device of claim 1, wherein the destination computing device is the simulation server, and the simulation server forwards the IOS filtered information to a destination portable computing device, the destination portable computing device being capable of displaying the IOS filtered information on a display of the destination portable computing device.
 7. The portable computing device of claim 6, wherein the destination user is currently executing the simulation on the destination portable computing device, the execution of the simulation on the destination portable computing device being controlled in real-time through interactions of the user with the IOS control and monitoring data displayed on the display via the user interface.
 8. The portable computing device of claim 1, wherein the destination computing device is the simulation server, and the simulation server forwards the IOS filtered information to a simulator, the simulator being capable of displaying the IOS filtered information on a display of the simulator.
 9. The portable computing device of claim 8, wherein the destination user is currently executing the simulation on the simulator, the execution of the simulation on the simulator being controlled in real-time through interactions of the user with the IOS control and monitoring data displayed on the display via the user interface.
 10. The portable computing device of claim 1, wherein the IOS filtered information consists in a subset of IOS information related to the selected at least one component, the subset being determined based on the destination user access rights.
 11. The portable computing device of claim 1, wherein the IOS control and monitoring data comprise one or more IOS User Interface (UI) pages.
 12. The portable computing device of claim 11, wherein the IOS filtered information comprises a subset of the one or more IOS UI pages, the subset being determined based on the destination user access rights.
 13. The portable computing device of claim 11, wherein the IOS filtered information comprises at least one filtered IOS UI page corresponding to an original IOS UI page, the components of the filtered IOS UI page comprising a subset of the components of the corresponding original IOS UI page, the subset being determined based on the destination user access rights.
 14. The portable computing device of claim 1, wherein the IOS control and monitoring data comprise a hierarchy of IOS UI pages, and the IOS filtered information comprises a subset of the hierarchy of IOS UI pages, the subset being determined based on the destination user access rights.
 15. The portable computing device of claim 1, wherein the processing unit generates IOS interaction data corresponding to interactions of the user with the IOS control and monitoring data displayed on the display via the user interface, and the processing unit transmits the IOS interaction data to the simulation server via the communication interface.
 16. The portable computing device of claim 1, further comprising memory for storing the simulation session data.
 17. A method for transmitting Instructor Operating Station (IOS) filtered information, the method comprising: receiving by a processing unit of a portable computing device IOS control and monitoring data from a simulation server via a communication interface of the portable computing device, the IOS control and monitoring data allowing a user of the portable to control execution of a simulation in real-time; receiving by the processing unit simulation session data via the communication interface of the portable computing device, the simulation session data comprising destination user access rights and an indication of a destination user that is currently executing the simulation; displaying by the processing unit the IOS control and monitoring data on a display of the portable computing device; receiving by the processing unit a selection by the user of at least one component of the IOS control and monitoring data displayed on the display, the selection being performed by an interaction of the user with the displayed IOS control and monitoring data via a user interface of the portable computing device; determining by the processing unit IOS filtered information as a subset of information related to the selected at least one component, the determination of the IOS filtered information taking into consideration the destination user access rights of the destination user currently executing the simulation; and transmitting by the processing unit the IOS filtered information to a destination computing device separate from the portable computing device via the communication interface.
 18. A non-transitory computer program product comprising instructions deliverable via an electronically-readable media, such as storage media and communication links, the instructions when executed by a processing unit of a portable computing device providing for transmitting Instructor Operating Station (IOS) filtered information by: receiving by the processing unit IOS control and monitoring data from a simulation server via a communication interface of the portable computing device, the IOS control and monitoring data allowing a user of the portable to control execution of a simulation in real-time; receiving by the processing unit simulation session data via the communication interface of the portable computing device, the simulation session data comprising destination user access rights and an indication of a destination user that is currently executing the simulation; displaying by the processing unit the IOS control and monitoring data on a display of the portable computing device; receiving by the processing unit a selection by the user of at least one component of the IOS control and monitoring data displayed on the display, the selection being performed by an interaction of the user with the displayed IOS control and monitoring data via a user interface of the portable computing device; determining by the processing unit IOS filtered information as a subset of information related to the selected at least one component, the determination of the IOS filtered information taking into consideration the destination user access rights of the destination user currently executing the simulation; and transmitting by the processing unit the IOS filtered information to a destination computing device separate from the portable computing device via the communication interface. 